System and method for pinning tabs in a tabbed browser

ABSTRACT

The techniques and mechanisms described herein are directed to a method for pinning a tab in a tabbed browser. Briefly stated, browsing software is configured to recognize a “pin” event, such as a hot key, a menu selection, and the like. Upon recognizing the pin event, the browsing software splits a display screen into a pinned window and a tabbed window. The tabbed window displays one or more open tabs and the content of the currently in focus tab. The pinned window may display content that was previously displayed within one of the tabs in the tabbed window or may display new content. The browsing software may configure the navigation of the pinned window differently than the navigation for the tabs in the tabbed window.

TECHNICAL FIELD

This document generally relates to browsing software, and moreparticularly, to tabbed-browsing software.

BACKGROUND

Browsing the World Wide Web (the web), the graphical portion of theInternet, has become quite popular in recent years. A software program,commonly referred to as a web browser, or just browser, provides aneasy-to-use point-and-click interface for accessing various content onthe web. Upon entering a web address or URL of a particular website, thebrowser requests web pages from a web server hosting that website. Thebrowser then interprets the web pages and displays the content on adisplay. The web pages include hypertext and hyperlinks that, whenselected, cause the browser to request additional content associatedwith them. By selecting the hypertext and hyperlinks, a user mayconveniently navigate through pages of information—commonly known asbrowsing or surfing the Internet.

Each time one of the hypertext or hyperlinks is selected, the newcontent is downloaded into the current window. Depending on the networkbandwidth, this may cause a brief to extensive delay. For convenience,additional windows may be opened to view multiple web pages. However,after opening several web pages, each in its own window, the taskbar maybecome quite cluttered. This makes it difficult to re-locate aparticular web page. Tabbed browsers have been introduced to help managethe viewing of multiple web pages.

Tabbed browsers load web pages in “tabs” within the same browser window.Therefore, only one item appears on the taskbar, even though multipleweb pages are loaded. Clicking on a hyperlink results in the web pagebeing downloaded in the background into another tab. This allows a userto continue viewing the current web page without automatically switchingto the other web page. When the web page is finished loading, the usermay click on the associated tab and view that web page. Tabbed browsingmakes it easier and more convenient to view multiple web pages.

The present mechanism further enhances the tabbed-browsing experience.

SUMMARY

The techniques and mechanisms described herein are directed to a methodfor pinning a tab in a tabbed browser. Briefly stated, browsing softwareis configured to recognize a “pin” event, such as a hot key, a menuselection, and the like. Upon recognizing the pin event, the browsingsoftware splits a display screen into a pinned window and a tabbedwindow. The tabbed window displays one or more open tabs and the contentof the currently in focus tab. The pinned window may display contentthat was previously displayed within one of the tabs in the tabbedwindow or may display new content. The browsing software may configurethe navigation of the pinned window differently than the navigation forthe tabs in the tabbed window. The pinned window provides a convenientway to compare multiple web sites, review content identified within insearch, and the like.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments are described with referenceto the following figures, wherein like reference numerals refer to likeparts through-out the various views unless otherwise specified.

FIG. 1 is an illustrative computer environment that may be used toimplement the techniques and mechanisms described herein.

FIG. 2 is a block diagram illustrating one embodiment of an architecturefor implementing tabbed browsing having a tab-pinning feature asdescribed herein.

FIG. 3 is a display illustrating one embodiment of a user-interface thatsupports the tab-pinning feature in a tabbed browser.

FIG. 4 is a display illustrating different entry points for thetab-pinning feature.

FIG. 5 is a display illustrating the use of a pinned tab in a comparisonscenario.

FIG. 6 is a display illustrating the use of a pinned tab in a searchscenario.

FIG. 7 is a display illustrating a mini-navigation bar associated withthe pinned tab.

FIG. 8 is an operational flow diagram generally illustrating a processfor displaying a pinned tab within a tabbed browser display.

DETAILED DESCRIPTION

Briefly, the techniques and mechanisms described herein are directed toa method for pinning one of the tabs within a tabbed window displayed bya browser. The pinned tab may then be utilized as a hub for selectingnews articles, as a search page for selecting additional sites, as acomparison page for comparing information from other sites, and thelike. The following discussion describes the pinning mechanism within abrowser that supports tabbed-heterogeneous windows. However, afterreading the following description, one skilled in the art couldincorporate a pinning mechanism into other types of tabbed browsers. Aswill be described in more detail below, the present tab-pinningmechanism provides a convenience that was unavailable until now.

Exemplary Computing Environment

The various embodiments of the tab-pinning mechanism may be implementedin different computer environments. The computer environment shown inFIG. 1 is only one example of a computer environment and is not intendedto suggest any limitation as to the scope of use or functionality of thecomputer and network architectures. Neither should the computerenvironment be interpreted as having any dependency or requirementrelating to any one or combination of components illustrated in FIG. 1.

With reference to FIG. 1, one exemplary system for implementing atab-pinning mechanism includes a computing device, such as computingdevice 100. In a very basic configuration, computing device 100typically includes at least one processing unit 102 and system memory104. Depending on the exact configuration and type of computing device,system memory 104 may be volatile (such as RAM), non-volatile (such asROM, flash memory, etc.) or some combination of the two. System memory104 typically includes an operating system 106, one or more programmodules 108, and may include program data 110. This basic configurationis illustrated in FIG. 1 by those components within dashed line 112.

Computing device 100 may have additional features or functionality. Forexample, computing device 100 may also include additional data storagedevices (removable and/or non-removable) such as, for example, magneticdisks, optical disks, or tape. Such additional storage is illustrated inFIG. 1 by removable storage 114 and non-removable storage 116. Computerstorage media may include volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information, such as computer-readable instructions, data structures,program modules, or other data. System memory 104, removable storage 114and non-removable storage 114 are all examples of computer storagemedia. Thus, computer storage media includes, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM,digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by computing device 100.Any such computer storage media may be part of device 100. Computingdevice 100 may also have input device(s) 118 such as keyboard 132, mouse134, pen, voice input device, touch input device, etc. Output device(s)120 such as a display, speakers, printer, etc. may also be included.These devices are well know in the art and need not be discussed atlength here.

Computing device 100 may also contain communication connections 122 thatallow the device to communicate with other computing devices 124, suchas over a network. Communication connection(s) 122 is one example ofcommunication media. Communication media may typically be embodied bycomputer-readable instructions, data structures, program modules, orother data in a modulated data signal, such as a carrier wave or othertransport mechanism, and includes any information delivery media. Theterm “modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia includes wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media. The term computer readable media as used herein includesboth storage media and communication media.

Various modules and techniques may be described herein in the generalcontext of computer-executable instructions, such as program modules,executed by one or more computers or other devices. Generally, programmodules include routines, programs, objects, components, datastructures, etc. for performing particular tasks or implement particularabstract data types. These program modules and the like may be executedas native code or may be downloaded and executed, such as in a virtualmachine or other just-in-time compilation execution environment.Typically, the functionality of the program modules may be combined ordistributed as desired in various embodiments.

An implementation of these modules and techniques may be stored on ortransmitted across some form of computer readable media. Computerreadable media can be any available media that can be accessed by acomputer. By way of example, and not limitation, computer readable mediamay comprise “computer storage media” and “communications media.”

Exemplary Architecture

FIG. 2 is a block diagram illustrating one embodiment of an architecture200 for implementing the tab-pinning mechanism as described herein.Architecture 200 includes one or more content windows 202. The contentwindow may be a web browser, a shell view, a word processingapplication/document, a spreadsheet application/document, a presentationapplication/document, a document viewer, or the like. Each contentwindow 202 is associated with its own toolbars/menus 204, custom bars206, status bars 208, and content 210, as needed. For example, custombars may include bars created to operate with search engines and thelike. As mentioned earlier, in traditional browsers, each browser windowconsumed space on a taskbar. Once a number of browser windows wereopened, the taskbar became very cluttered. For the present tabbedbrowser, a tab window manager 220 handles all the content windows 202via their respective tab window 212. The tab window manger 220communicates with a browser frame 214. In addition, browser frame 214communicates with a navigation bar 216, a frame command bar 218, and atab user-interface 222. Each of these components will be described belowin more detail after describing thread boundary 230.

Thread boundary 230 represents a boundary between a single thread (i.e.,a frame thread) that handles the processing for the components shown tothe left of thread boundary 230 and multiple threads that handle theprocessing for the components on the right of thread boundary 230. Eachinstance of content window 202 is associated with at least one of itsown threads. That thread also handles the processing for the associatedtoolbars/menus 204, custom bars 206, status bars 208, and content 210.

By having multiple threads, at least one for each content window 202,the architecture prevents a potential bottleneck caused by having onlyone thread handle the messages for all HTML rendering across themultiple tabs. In addition, having multiple threads reduces thelikelihood of unnecessary delays or timeouts when downloading web pages.Having multiple threads also makes the architecture more resilientbecause if a tab hangs, only one tab hangs instead of potentiallyhanging all of the tabs. This is in contrast with other tabbed browsersthat host their tabs on a single UI thread. In these tabbed browsers,the entire application hangs when a single tab is blocked. Eachindividual thread may be prioritized.

Each of the components in architecture 200 is now described. Asmentioned above, each content window 202 is associated with its owntoolbars/menus 204, custom bars 206, status bars 208, and content 210,as needed. For example, if there are five tabs open, five instances ofeach add-on (e.g., custom bar, toolbar, etc) are created and hooked totheir own content. Similarly, if menus or status bars are modified viainternal logic, HTML, document hosting, add-ons, or the like, the menuor status bar associated with that content window 202 is changed. Theadd-ons and the content window 202 operate in a well know manner.Because the add-ons do not know about tabs, the architecture 200 doesnot modify the operation between the add-ons and the content window.Instead, the architecture wraps each set of content windows into onebrowser frame 214. While not shown, there may be multiple browser frames214, each with a set of tabbed-heterogeneous windows.

Content window 202 maintains state for the content window, such as size,position, visibility of frame elements, and the like. The state may bepersisted into a stream when the tabbed browser closes, and then may beread when a new content window is launched. Alternatively, the state maybe saved in a registry and read from the registry when the new contentwindow is launched.

The tab window 212 lives on the frame thread. Each tab window 212 isconfigured to manage communication between the outer frame components(e.g., navigation bar 216, browser frame 214, etc) and an individualtab. The tab window 212 holds pointers to its associated content window202 and interfaces so that it can manage cross-thread communicationbetween the outer frame components and the individual content window202. The cross-thread communication may involve cross-thread calls. Inone embodiment, calls from the browser frame 214 to the content window202 may be asynchronous. The tab window 212 is then responsible formarshalling the parameters and posting a message to the main window ofcontent window 202. In contrast, calls from the content window 202 tothe frame browser 214 may be synchronous. The tab window 212 is thenresponsible for marshalling the interfaces of the corresponding tabwindow 212. The tab window 212 may also convert synchronous calls intoasynchronous calls in order to reduce the likeliness that a tab willhang.

The tab window 212 may also cache a limited amount of state. This allowsthe tab window to provide a quick synchronous lookup of state to othercomponents. When the tab window 212 receives an event from the contentwindow 202 that modifies the state, the tab window propagates theseevents up to the tab window manager 220.

In addition, the tab window 212 exposes several operations that can beperformed on a tab, such as destroy, set visibility, set size, setposition, and order. The tab window 212 also exposes operations that theframe needs for asynchronously invoking a tab. These operations may beexposed via individual application programming interfaces (API) orthrough a generic API. For the present tab-pinning mechanism, each tabwindow 212 may have its own set of characteristics. For example, one ofthe tab windows may be a pinned window which has a slightly differentnavigation characteristic than other tabbed windows. The navigationcharacteristic for the pinned window may drive one of the other tabbedwindows instead of refreshing itself when a link is activated on thepage within the pinned window.

The tab window manager 220 hosts multiple content windows 202 viamultiple tab windows 212. The tab window manager 220 manages the overallstate of each of the tabs. The state may include: a top level URL; apage title; a back/forward button availability; a favorite icon for thecurrent page, a progress state for the current page, securityinformation reflected in the user-interface (e.g., HTTPs info); and thelike. The tab window manager 220 may synchronously query the tab window212 for per-tab data. In addition, the tab window manager 220 managesthe operations performed on the tabs, such as open, close, select, move,set size, set position, set order, and the like. This is achieved byaccessing the operations exposed via the tab window 212.

The browser frame 214 hosts the navigation bar 216, frame command bar218, tab window manager 220, and the tab UI 222. The browser frame 214may also directly or indirectly host a rebar control (not shown). Thebrowser frame 214 brokers communication between these hosted components.

The tab UI 222 is configured to render the user-interface for thecollection of tab windows 212. In addition, the tab UI 222 controls therectangle for the tabs' browser region. Tab UI 222 receives events fromtab window manager 220 via browser frame 214. The events pertain to thetabs being managed by tab window manager 220. The events include an“OnTabListChanged” event, an “OnTabChanged” event, an “OnTabPinned”event, and the like. The “OnTabListChanged” event is sent by tab windowmanager 220 when changes are made to a collection of tabs (e.g., Open,Close, Reorder, etc). The “OnTabPinned” event is sent by tab windowmanager 220 when a tab has been pinned. The “OnTabChanged” event is sentby tab window manager 220 when a single tab changes (e.g., progress,title, URL). The corresponding tab window 212 sends a notification totab window manager 220 which forwards the notification to tab UI 222.The notification identifies the tab. This method of communication keepsthe communication serialized. In an alternate embodiment, individual tabwindows 212 may directly call into tab UI 222. In addition, there may bemultiple tab UI 222 components, each one handling the same set of tabs,but for a different location on the user-interface. For example, one tabUI may handle a tab row along the top of the display and another tab UImay handle a tab listview along the side of the display.

The frame command bar 218 provides a set of commands that have beendetermined to be the most useful to the tabs. By having this set ofcommands readily available for any tab, a user can conveniently locateone of the commands for any tab.

Exempkary User-Interface

FIG. 3 is one embodiment of a display illustrating a user-interface 300that supports pinning tabs as implemented within a tabbed browser.User-interface 300 illustrates salient portions of a tabbed browser thatimplements the present tab-pinning mechanism. Those skilled in the artwill appreciate that optional third party toolbars (not shown), a pagespace control (not shown), a status bar (not shown) and/or custom bars(not shown) may also be included within user-interface 300 withoutdeparting from the present tab-pinning mechanism. As shown,user-interface 300 includes a navigation bar 302, a pinned window 340,and a tabbed window 320.

The tabbed window 320 includes, a tab band 322, one or more tabs (e.g.,tabs 324, 326, and 328), and content 336 associated with the tabcurrently in focus (e.g., tab 324 shown in FIG. 3). Each of the tabs324, 326, and 328 may include a close box (e.g., close box 332) forclosing the respective tab. In addition, tabbed window 320 may include anew tab 330 for creating a new tab within the tabbed window 320. Asadditional tabs are opened, the visible portion of each tab is reducedto accommodate the additional tabs.

In accordance with the present tab-pinning mechanism, the tabbed browserprovides a mechanism for signaling a pin-tab event. The mechanism may bea pin icon 334, a context menu selection (not shown), and/or the like onthe user-interface 300. The mechanism may also be a hot key (not shown)entered through a keyboard. Upon receiving the pin-tab event, the tabbedbrowser splits the display to accommodate the addition of a pinnedwindow 340 to an existing tabbed window 320. The tabbed browser softwaremay reduce the size of the tabbed window 320 to accommodate the pinnedwindow 340.

The pinned window 340 includes a pinned tab 342 and pinned content 346associated with the pinned tab 342. In addition, the pinned window 340may include a pin close box 344 for the pinned tab 342. When the pinclose box 344 is selected, the pinned window 340 may close so that onlythe tabbed window 320 remains on the display. However, before closingthe pinned tab 342, the pinned tab 342 and the pinned content 346 may betransferred to a new or existing tab within the tabbed window. Thisallows the pinned content 346 to still be available for other purposes.

The navigation bar 302 may include an address bar 304, a back button306, a forward button 308, and a search box 310. The content of theaddress bar 304 may be maintained for each tab. Thus, when “clicking”through the tabs 324, 326, and 328, the address bar 304 may display theaddress for the currently selected tab (i.e., the tab in focus). Whenthe tab band 322 is in focus, the back button 306 may change theselected tab to be the tab to the left of the currently selected tab inthe tab row. The forward button 308 may change the selected tab to bethe next tab in the tab row moving to the left. The search box 310allows text to be entered and searched for in the currently selectedtab. One will note that the content of the address bar 304 may depend onwhether the tabbed window 320 or the pinned window 340 is in focus. Whenthe pinned window 340 is in focus, the address bar 304 may display theaddress for the content in the pinned window. Likewise, the back button306 and the forward button 308 may depend on whether the tabbed window320 or the pinned window 340 is in focus. When the pinned window 340 isin focus, the back button 306 and the forward button 308 may be used toview previous web pages that were visited.

In one embodiment, items in the user-interface 300 that are per frameinclude the navigation bar 302, the tab band 322, and the pinned window340. Items in the user-interface 300 that are per tab include content336. Interestingly, in one embodiment, content 336 may include differenttype of data sources. For example, content 336 may be a web page, ashell folder, a navigation based application, and the like. Thisheterogeneous content may be hosted in a single frame. In anotherembodiment, the content 336 associated with each tab may all be webpages.

The present tab-pinning mechanism provides a great convenience in manydifferent scenarios. FIGS. 4-6 illustrate two scenarios in which a usermay utilize the present tab-pinning mechanism. The first scenario (FIG.4-5) is when a user wishes to compare items from different web pages. Inthe past, in order to achieve this, the user would have had to openseveral windows and then position each one in a desirable configurationfor viewing and comparing. FIG. 6 illustrates a search scenario where auser performs a search and selects the desired web pages from the listof returned web pages. In the past, when one of the desired web pageswas selected from the list, the search page would have been replacedwith the content from the desired web page. The user would then have tonavigate back to the search page to select another desired link.

FIG. 4 is a display 400 illustrating different entry points for creatinga pinned tab. A user uses tabbed browsing software 402 to view (or“surf”) various content on the Internet, local network, local computer,and the like. The user places the content of interest into one or moretabs (e.g., tabs 404-412). In the example shown, the user has visitedseveral websites to learn about different types of digital cameras. Theuser now wishes to compare the different types of cameras with eachother. The user may put the tab that describes the user's favoritedigital camera in focus (e.g., tab 404 in focus) by selecting theassociated tab. The user may then initiate the present tab-pinningmechanism through one of several entry points. One entry point is viathe user's selection of the pin icon 420. Another entry point may be viathe user's selection of a pin tab menu selection 432 from a context menu430. Still another entry point may be via the user's entry of a hotkey/hot key sequence on a keyboard. These and other entry pointsinitiate the tab-pinning mechanism by signaling a pin-tab event to thetabbed browsing software.

FIG. 5 is a display 500 illustrating the result when the pin-tab eventis received. Continuing with the comparison scenario, the tab that wasin focus when the tabbed browsing software received the pin-tab event,is transferred to the pinned window 510. Thus, tab 404 shown in FIG. 4is now pinned tab 504 within the pinned window 510. The content of theuser's favorite digital camera review is “pinned” in pinned window 510.The user can now click the other tabs 406-410 within the tabbed window512 to easily compare their respective content with the pinned content.One will note that even though tab 404 is shown removed from the tabbedwindow 512, in another embodiment, tab 404 may remain available intabbed window 512. This embodiment allows the user to compare differentportions of the same content.

FIG. 6 is a display 600 illustrating the use of a pinned tab in a searchscenario. The entry point for the tab-pinning mechanism in this searchscenario may be based on a specific user action, such as entering asearch request within a search engine. For this embodiment, the tabbedbrowser software is configured to recognize this specific user actionand to split the display into a pinned window 602 and a tabbed window604. The tabbed browser software is further configured to display theresults of the search in the pinned window 602. The tab window 604 maybe initially empty or may contain existing tabs that were open in thetabbed window when the search was initiated. The tabbed browsingsoftware may also be configured to modify the navigation characteristicof the pinned window 608 so that links (e.g., links 602, 604, and 606)within the pinned window 602 drive tabs within the tabbed window 604.For example, selection of link 602 may create a new tab 612 with thecontent associated with link 602. Likewise, selection of link 604 and606 may create new tabs 614 and 616, respectively. The tabbed browsingsoftware may also be configured to allow links (e.g., link 608) thattarget themselves to update the pinned content with new content. Thus,in the search scenario, when the link associated with the second page ofresults is selected (link 608), the pinned content for the first page ofresults is replaced with the second page of results.

FIG. 7 is a display illustrating a mini-navigation bar 710 associatedwith a pinned tab. For this embodiment, the pinned window 700 includesthe mini-navigation bar 710. The mini-navigation bar 710 includes amini-back button 712, a mini-forward button 714, and a mini-address 716.The mini-navigation bar 710 allows the tab to be navigated using thosecontrols. The operation of the controls are similar to the operation ofthe back button 306, the forward button 308, and the address 304 whenthe pinned tab is in focus. However, the mini-navigation bar 710 mayprovide a more convenient method for navigating within the pinned windowbecause the user does not need to keep changing the focus between thetabbed window and the pinned window.

Exemplay Operation

FIG. 8 is an operational flow diagram generally illustrating a processfor displaying a pinned tab within a tabbed browser display. The process800 may be implemented on a computing device, such as computing device100. The process 800 may be implemented within operating system 106, asone or more program modules 108, or in a combination of the two. Theprocess begins at step 802 where tabbed browsing software receives apin-tab event. As described above, the pin-tab event may be via a hotkey entry, a selection of a pin icon, a selection of a menu item,initiation of a specific action, such as a search, or the like.

At step 804, the display is split so that there is a pinned window and atabbed window. The split may allow half the display for the pinnedwindow and the other half for the tabbed window. In another variation,the pinned window may have one-third of the display and the tabbedwindow may have two-thirds of the display. The split may occurvertically or horizontally. These and other variations are envisioned.However, it is desirable to split the display in a manner that allowsthe content of the pinned window to be easily viewed.

At step 806, the content for the pinned window is displayed. Dependingon the pin-tab event, the content may be new content or may be existingcontent from one of the tabs within the tabbed window. For example, ifthere are several tabs open in the tabbed window, the content of the tabassociated with the hot key may be displayed in the pinned window.However, if a search is initiated in one of the tabs in the tabbedwindow, the search results (i.e., new content) may be displayed in thepinned window.

At step 808, the tab in the tabbed window that has the same content asin the pinned window may be optionally removed from the tabbed window.This optional removal of the same content is especially desirable if acomparison is being performed between the pinned window and the othertabs in the tabbed window.

At step 810, the characteristics of the pinned window may be modified.For example, if the pinned window is used in a search scenario or a hubscenario, it may be desirable to have the navigation of the clickedlinks occur in the tabbed window rather than within the pinned window.In these scenarios, activating a link within the pinned window drivesthe creation of a new tab in the tabbed window that displays contentassociated with the activated link. However, the pinned window may allowa specific link that targets itself to update the pinned window. Forexample, a search page may have one or more links to subsequent searchpages. If a user selects one of these additional search pages, the newsearch page will replace the current search page in the tabbed windowinstead of opening a new tab in the tabbed window. Thus, in oneembodiment, when the tabbed browsing software recognizes an anchor tagthat has a target property that identifies itself as the target, thetabbed browsing software will navigate in place within the pinnedwindow. The default navigation characteristic may be to re-direct thelink to another tab within the tabbed window.

Reference has been made throughout this specification to “oneembodiment,” “an embodiment,” or “an example embodiment” meaning that aparticular described feature, structure, or characteristic is includedin at least one embodiment of the present invention. Thus, usage of suchphrases may refer to more than just one embodiment. Furthermore, thedescribed features, structures, or characteristics may be combined inany suitable manner in one or more embodiments.

One skilled in the relevant art may recognize, however, that the presentmechanism may be practiced without one or more of the specific details,or with other methods, resources, materials, etc. In other instances,well known structures, resources, or operations have not been shown ordescribed in detail merely to avoid obscuring aspects of the presentconsistent visual appearance technique.

While example embodiments and applications have been illustrated anddescribed, it is to be understood that the present technique is notlimited to the precise configuration and resources described above.Various modifications, changes, and variations apparent to those skilledin the art may be made in the arrangement, operation, and details oftechnique disclosed herein without departing from the scope of theclaimed invention.

1. A computer-implemented method for displaying content in tabbedbrowsing software, the method comprising: receiving a pin-tab event inresponse to a user action; in response to the pin-tab event, splitting adisplay to accommodate a pinned window in addition to a tabbed window,the tabbed window displaying a plurality of tabs where each tab isassociated with its respective content, the respective content beingdisplayed when the corresponding tab is in focus; and displaying pinnedcontent within the pinned window based on the pin-tab event.
 2. Thecomputer-implemented method of claim 1, wherein the pinned content isthe content associated with the tab in focus.
 3. Thecomputer-implemented method of claim 1, wherein the user actioncomprises entry of a hot key.
 4. The computer-implemented method ofclaim 1, wherein the user action comprises selection of a menu item. 5.The computer-implemented method of claim 1, wherein the user actioncomprises selection of a pin icon.
 6. The computer-implemented method ofclaim 1, wherein the user action comprises entry of a search request toa search engine.
 7. The computer-implemented method of claim 6, whereinthe pinned content comprises results from the search request.
 8. Thecomputer-implemented method of claim 1, further comprising removing thetab from the tabbed window that has the same content as the pinnedcontent.
 9. The computer-implemented method of claim 1, furthercomprising modifying the characteristics of the pinned window.
 10. Thecomputer-implemented method of claim 9, wherein the characteristics ofthe pinned window related to navigation of links within the pinnedwindow are modified in a manner such that activating a link within thepinned window drives one of the tabs within the tabbed window.
 11. Thecomputer-implemented method of claim 10, wherein the characteristics ofthe pinned window are further modified to allow a link that targetsitself to update the pinned window when activated.
 12. Thecomputer-implemented method of claim 1, further comprising displaying amini-navigation bar associated with the pinned window for navigationwithin the pinned window.
 13. A computer-readable medium havingcomputer-executable instructions for displaying content in atabbed-browsing software, the instructions comprising: receiving apin-tab event in response to a user action; in response to the pin-tabevent, splitting a display to accommodate a pinned window in addition toa tabbed window, the tabbed window displaying a plurality of tabs whereeach tab is associated with its respective content, the respectivecontent being displayed when the corresponding tab is in focus; anddisplaying pinned content within the pinned window based on the pin-tabevent.
 14. The computer-readable medium of claim 13, wherein the pinnedcontent comprises the content associated with the tab in focus.
 15. Thecomputer-readable medium of claim 13, wherein the user action comprisesan entry of a hot key, selection of a menu item, selection of a pinicon, or entry of a search request in a search engine.
 16. Thecomputer-readable medium of claim 15, wherein the pinned contentcomprises results from the search request.
 17. The computer-readablemedium of claim 13, further comprising removing the tab from the tabbedwindow that has the same content as the pinned content.
 18. Thecomputer-readable medium of claim 13, further comprising modifying thecharacteristics of the pinned window related to navigation of linkswithin the pinned window, the characteristic being modified in a mannersuch that activating a link within the pinned window drives one of thetabs within the tabbed window.
 19. The computer-readable medium of claim18, wherein the characteristics of the pinned window are furthermodified to allow a link that targets itself to update the pinned windowwhen activated.
 20. A system configured to pin tabs within a tabbedbrowser, the system comprising: a processor; and a memory into which aplurality of computer-executable instructions are loaded, the pluralityof instructions performing a method comprising: receiving a pin-tabevent in response to a user action; in response to the pin-tab event,splitting a display to accommodate a pinned window in addition to atabbed window, the tabbed window displaying a plurality of tabs whereeach tab is associated with its respective content, the respectivecontent being displayed when the corresponding tab is in focus; anddisplaying pinned content within the pinned window based on the pin-tabevent.